* templates: consider `uint`s for comparison in `in`

For unknown reasons, `in` did not consider `uint`s for comparable types,
forcing users to a) be extremely confused why their code doesn't work
when it should and b) figuring a way around that (either by type
conversion or some other arguably unnecessary things).

Adjust the definition of `in` to consider `uint`s.
Future considerations: can we somehow rewrite this using generics,
elimiating the need to exhaustively list all possible comparable types?

Signed-off-by: Luca Zeuch <l-zeuch@email.de>

* templates: [in] use CanUint and friends, modernise for-loop

Signed-off-by: Luca Zeuch <l-zeuch@email.de>

---------

Signed-off-by: Luca Zeuch <l-zeuch@email.de>

…essage create events (#1975)

* use templates.SDict for modal values

* component functions re-org

…er is logged out (#1979)

…ice in AddComponents

Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.43.0 to 0.45.0.
- [Commits](golang/crypto@v0.43.0...v0.45.0)

---
updated-dependencies:
- dependency-name: golang.org/x/crypto
  dependency-version: 0.45.0
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

…1985)

* return error from sendMessage to handle it in try catch in  template

* return error from sendMessage to handle it in try catch in  template

* added twitch feeds

* added env vars to example docker

* simplified logic to send notifications

* Fix bugs with VOD

* Deleted an annoying space

* Second annoying space

… 15 minutes (#1992)

* Added logic to restart reddit feed if the last success was older than 15 minutes

* call check feed in start feed

* fixes to the exit logic in case of feed shutdown

This allows users to at least bypass silly permission restrictions for
debugging their custom command triggers.

Joe suggested it, I was faster than him.

Signed-off-by: Luca Zeuch <l-zeuch@email.de>

…d, modified the default custom announcement to share vod link instead of stream link (#2011)

… has to send a message (#2015)

…roup, preference is cc-error-channel, group-error-channel, trigger channel (#2016)

…case an event for an already joined member is received (#2018)

This reverts commit a498b89.

* moderation: restore clean command's -nopin flag

Add the `"pinned"` message field to dstate.MessageState rather than
fetching the channel's pinned messages for filtering
Also clean up some cruft while we're here

Signed-off-by: Galen CC <galen8183@gmail.com>

* dstate tracker: update all message fields in handleMessageUpdate

MESSAGE_UPDATE events send the same fields as MESSAGE_CREATE, so we can
reuse dstate.MessageStateFromDgo rather than duplicating logic in
handleMessageUpdate

Signed-off-by: Galen CC <galen8183@gmail.com>

* dstate: return earlier in handleMessageUpdate

Signed-off-by: Galen CC <galen8183@gmail.com>

---------

Signed-off-by: Galen CC <galen8183@gmail.com>

* migrated to new pin endpoints

* reduce pin list/count usage limit.

* discordgo: fix EndpointChannelMessageCrosspost

Signed-off-by: Galen CC <galen8183@gmail.com>

* discordgo: use EndpointChannelMessage in EndpointChannelMessageCrosspost

Signed-off-by: Galen CC <galen8183@gmail.com>

---------

Signed-off-by: Galen CC <galen8183@gmail.com>

…on (#2022)

Add a `memberAbove` function for use in custom commands. Currently,
users have to write a fair bit of code to perform hierarchy checks. This
convenience function condenses it down to a single line.
It reports whether member a is above member b.

Usage:

```
{{ $isAbove := memberAbove <a> <b> }}
```

Both `a` and `b` must be a member object.

See https://discord.com/channels/166207328570441728/356486960417734666/1469137169242128415

Signed-off-by: Luca Zeuch <l-zeuch@email.de>

…bot is run in sharded mode across several servers (#2025)

…r manage events (#2029)

Each command had outdated permissions. After speaking with des, it appears that a lot of the permissions were not what they were supposed to be. Des proposed the idea of moving the permissions to the "new" event related permissions. This commit does exactly that, whilst also keeping manage guild for all command requirements. 

"Create" also now has required permissions, whereas previously it did not (appears to be unintentional). Every command should now require the same permissions.

…o modals (#2013)

…uncs.js